Fix broken links to the React 19 Upgrade Guide - #8601
Conversation
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
|
These links aren't currently broken — vercel.json (L248) permanently redirects /blog/2024/04/25/react-19 → /blog/2024/12/05/react-19, and the fragment is preserved, so they land on the right headings today. The new target is the problem: react-19-upgrade-guide.md doesn't define {/error-handling/} or {/ref-as-a-prop/} — those headings live in blog/2024/12/05/react-19.md (L727 and L396). So after this change the pages load but drop the reader at the top of the wrong post, which a link checker won't flag. If the goal is to skip the redirect hop, the repo already has a convention for that — useImperativeHandle.md:49 links straight to /blog/2024/12/05/react-19#ref-as-a-prop. Retargeting to that path instead would work. |
|
Thanks for catching this! |
4f05843 to
cffbd7f
Compare
cffbd7f to
5b3a751
Compare
|
I updated the references to point to the correct React 19 blog anchors. The changes are now limited to the affected docs links. Appreciate the review! |
The #error-handling and #ref-as-a-prop anchors live in /blog/2024/12/05/react-19, not in the upgrade guide. Point the three links at the correct post so they land on the right headings.
* Document browser-only rendering Add the Canary browser API reference, including optional lazy reasons, server bailout reporting, fatal and abort behavior, navigation entries, and onBrowserBailout options for every streaming, resume, and prerender API that supports it. * Polish browser API docs and add live example * Document browser with use and Suspense --------- Co-authored-by: Aurora Scharff <aurora.sofie@gmail.com>
* Clarify browser-only rendering guidance * Polish browser-only guidance wording * Use Canary markers in browser guidance * Present browser as a use resource * Polish browser usage labels * Address browser guidance review * Clarify browser return value is opaque * Restore alternative wording * Restore hydration alternative wording * Focus use introduction on resources * Note stable browser cleanup
* Pin matching React Canary versions in Sandpack demos * Use cached Canary build in Sandpack demos
* Improve browser-only rendering example * Clarify browser-only example action * Show browser-only fallback on reload
5b3a751 to
1dc349c
Compare
5 participants
Three links still used the old
/blog/2024/04/25/react-19path, which 404s since the page was renamed toreact-19-upgrade-guide. Updated them to the current path.